Conversation
akutz
force-pushed
the
feature/vm-min-hw-version
branch
2 times, most recently
from
63d38d4 to
efe31b8
Compare
This patch adds support for specifying a VM's mininum hardware version in order to enable more control over a VM's hardware version by the DevOps persona. This also enables upgrading brownfield VMs to a more recent hardware version in order to support features like PVCs and Dynamic Direct Path I/O devices.
akutz
force-pushed
the
feature/vm-min-hw-version
branch
from
efe31b8 to
51f0fbc
Compare
|
Change looks good to me. We'll need to decide on what takes precedence when the VM Class Config Spec's hw version and the VM Spec's hw version are set. VM Spec overrides Class?. |
I misread the above point. The VirtualMachineSpec.MinHardwareVersion always has final say, whether the original value is derived from the OVF or eventually VM Class. Thanks for the approvals -- I'm going to wait to merge this until we have go-ahead for Shruthi to execute on the implementation. We don't want to add the field until we know we can resource the work to make it available in the next release. |
3 participants
This patch adds support for specifying a VM's mininum hardware version in order to enable more control over a VM's hardware version by the DevOps persona. This also enables upgrading brownfield VMs to a more recent hardware version in order to support features like PVCs and Dynamic Direct Path I/O devices.